Skip to content

Conversation

GIBZ-GIPE
Copy link
Contributor

@GIBZ-GIPE GIBZ-GIPE commented Sep 17, 2025

I am submitting

  • a new package
  • an update for a package

Description: This is a template package to be used by teachers at GIBZ for creating teaching materials. Despite the uniform layout of materials, it provides several styled components for often used content elements such as hints, questions, tasks and others.

I have read and followed the submission guidelines and, in particular, I

  • selected a name that isn't the most obvious or canonical name for what the package does

  • added a typst.toml file with all required keys

  • added a README.md with documentation for my package

  • have chosen a license and added a LICENSE file or linked one in my README.md

  • tested my package locally on my system and it worked

  • excluded PDFs or README images, if any, but not the LICENSE

  • ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

@typst-package-check typst-package-check bot added the new A new package submission. label Sep 17, 2025
@saecki saecki self-assigned this Sep 19, 2025
Copy link
Member

@saecki saecki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this package! I've left a few comments regarding the name and description, and the readme needs to be updated.

@typst-package-check typst-package-check bot changed the title script-gibz:0.1.0 gibz-script:0.1.0 Sep 19, 2025
@saecki
Copy link
Member

saecki commented Sep 29, 2025

Sorry for the slow response! I see there are now changes from other packages included in this PR, did you merge the main branch back into your fork? Could you rebase onto main, so this PR does only include the changes from this package?
If you're not familiar with git, I think the easiest way would be to first back up your package files, then sync your fork discarding all changes. And then create a new commit with your copied package files.

@GIBZ-GIPE
Copy link
Contributor Author

@saecki I hopefully did what you suggested :-)

@saecki
Copy link
Member

saecki commented Sep 30, 2025

Thanks, yeah looks good!

@saecki saecki merged commit 0ba7b2c into typst:main Sep 30, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new A new package submission.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants